Remove Extra Space Before "stackTrace" in Error Payload JSON #198
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks a lot @math-hiyoko and very sorry about the delay! |
maxday
approved these changes
Apr 29, 2025
godcrampy
approved these changes
Apr 29, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summery
This PR addresses the issue reported in #197 regarding the unnecessary space found before the "stackTrace" key in the generated JSON error payload. The presence of this space affects the consistency of the JSON formatting without impacting the functionality or parseability of the output. This minor change aims to enhance the readability and the overall quality of the code by maintaining a consistent JSON format.
Changes
The extra space before the "stackTrace" key in the JSON string construction has been removed.
Before
After